Proposal for WCAG

Editors notes: This document has been moved to github at https://rawgit.com/w3c/coga/master/extension/index.html

this document is out of date

The following is for a first draft for the extension for COGA for further discussion with WCAG. It is based on the user research at https://w3c.github.io/wcag/coga/user-research.html and the issue papers available at https://rawgit.com/w3c/coga/master/issue-papers/index.html.

The supporting techniques and further descriptions of the success criteria, as well as information on who it helps and why, are described in more detail in https://rawgit.com/w3c/coga/master/techniques/index.html.

Detailed descriptions of users and the challenges, persona, and research sources are given in the user research document above This proposal for the WCAG extension includes changes in the levels of WCAG 2.0 success criteria, new success criteria and new supportive techniques.

We have identified the following themes:

1. Help as many users as possible understand the site and know how to use it. This often involves using things that are clear and familiar to the user so that they do not have to learn new symbols, terms or design patterns. Personalization and good use of semantics can help make the symbols and design as familiar to the user as possible.
2. Prevent the user from making mistakes and make it easy to correct mistakes when they do occur. A good design and use of scripts will make errors less likely, but when they do occur the user should know how to correct them, without having to render other data or start from the beginning.
3. Help the user focus and restore context if attention is lost. Items like breadcrumbs can help orientate the user and help the user restore the context when it is lost. (Making breadcrumbs clickable can also help the user undo mistakes.)
4. Minimize the cognitive skills required to use the content and avoid barriers that stop people with cognitive disabilities from using content, such as hard to use security mechanisms. When possible, provide more accessible options.

Note this is a first draft. We anticipate some additions such as techniques for multi-media. However most techniques can be applied to any media, such as dividing your content into sections and using a clear heading for each section. For multi-media it should be easy to go back to each section using techniques such as indexing and bookmarks.

New success criteria

Note that we will be adding a simple language equivalent for this page when we have agreed on the content

Under WCAG 1.3 - Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

We suggest adding the following as success criteria:

Use semantics and safe standardized techniques that enable the content to be adapted to the user scenario including enabling additional support and personalization.

• Define - Safe standardized techniques: Standardized by wcag, other w3c groups, or by the platform, browser or operating system where user vulnerabilities are not exposed without informed consent (this will be a discussion and is not yet finalized.)
• Define personalization as user defined (maybe change the word to individualization).
• Define enabling additional support.

Note that techniques will included: 
#Use semantics and standardized techniques  to provide extra help (COGA Techniques 4.1)
#Provide symbols on key content  (COGA Techniques 4.2)
#Include features that support the user preferences
#Enable user agents to find the version of the content that best fits their needs

See also: Multi-Modal Content Delivery (was:Semantics and standardized techniques that enable adaptivity are used when available)

Under WCAG 2.2 Provide users enough time to read and use content.

We suggest adding the following as success criteria:

Timed event are not used except for the situations listed below.

(See COGA Techniques 2.9.1 )

1. Sessions time out after 20 hours have elapsed
2. Where security may be at risk a session can time out after half an hour of disuse
3. Where financial or sensitive information is at risk the time out can be shorter
4. Timing is essential to the function of the content - such as some tests.

Where there is an exception, the content must conform to WCAG 2.2.1 Timing Adjustable, so long as

1. The function to turn off, adjust or extend the timing are controlled by simple action and labeled with simple text.
2. A user settable time minimum must be provided to complete any controlling action. Note that all user setting must be easy to set and use standardized techniques when available (see previous definition).
3. The user can be made aware of the time out limits, including the length of the warning - this condition may be deleted
4. The user can easily return to the same point in a task, without data loss.
   1. as the default
   2. standardized system setting (example the user can set that the data is not stored)
   3. option to set user preference that has a conformance interface and is directly available at each stage of the task.

 Techniques with examples are needed such as a dialog on opening the app that seas do you want your old stuff
 

(Compare to WCAG 2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) however the options is not useful for COGA- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; etc.

To define sensitive information as information that can put people at risk or information the user wishes to protect (To do - add examples including the user sets the time out)

Under WCAG 2.3

Guideline 2.3 "Do not design content in a way that is known to cause seizures" should be changed to: Guideline 2.3 "Do not create mechanisms that are know to potentially harm the user."

Exclusion: Mechanisms that are know to potentially harm do not include selling products know to be harmful.

We suggest adding the following as success criteria:

Do not expose user information in a way that can be exploited without informed consent

Techniques to include:  using functional requirements for personlzation that do not suggest that the majority of users are disabled. Failure technique to be added of identifying a user to a code that is used mainly for people with dyscalculia.

Do not add mechanisms that are likely to confuse the user in a way that may do them harm

Techniques to include: not adding automatically incrementing the number of items selected without warning the use

Under WCAG 3.1

We suggest adding the following as success criteria:

Provide a clear structure that includes:

(See COGA Techniques 2.1)

• Headings and labels are provided that describe the topic or purpose of each section and are easy to find. (COGA Techniques 2.1.2).
• Consistent styles are used for the same type of information (COGA Techniques 2.1.1). To define same type of information as information with the same role, such as warnings, key points, errors, news items headings of the same importance etc.
• Maintain a consistent look and behavior for icons, navigational elements and controls across a set of pages.
• Structure and relationships are visually obvious such that over 90% of users can immediately identity the structure and relationships (COGA Techniques 2.1.1)
• Paragraphs are separated by additional space
• Lists are used (COGA Techniques 2.1.1)
• Time - Check use of appropriate punctuation between numbers when providing times as these may be read inappropriately by text to speech engines.
• Information is provided in manageable chunks, that include:
  • One idea per paragraph. (One sentence is enough for a paragraph.)
  • Have one point per sentence. Long sentences can often be broken up into short sentences or lists. If a sentence can use more than two sections, it typically can be broken up.

(sections are defined as divided by a conjunction e.g. coma)

• Provide a clear font and layout. A clear font and layout is one that is:
  • backed up by user research where coga users are part of the user testing or,
  • identified in a known WCAG technique or,
  • identified by the user preferences (preferred)

Techniques will include: using size, emphasis , colour, symbols, white space and positioning 

Exception: If a specific structure is an essential part of the main function of the site.

Interactive controls are visually clear or visually clear controls are easily available that conform to the following:

(See COGA Techniques 2.3)

1. Interactive controls are visible
2. Interactive controls including links are visually discriminable and their boundaries are visually clear.
   1. Boundaries on interactive controls and boundaries of icons should have a sufficient color contrast of 1.5.
3. Interactive controls with the same role are consistently presented across a set of web pages
4. The qualities or properties of the control define its possible uses. It is clear how it can or should be used and what action it will trigger.

Actions and actionable items that can be interacted with should have a clear visual style that indicates how to interact with them e.g. buttons that look like buttons. Visually clear controls can be made easily available though easy to use personlization (when available)

Technique will include: additional controls are under a sub menu item such as a button that reads "show toolbar"
Technique will include:  1. Using techniques like 'flat design' with great care as they have reduced affordances. 2. the web author needs to define buttons  and the OS has a setting called show clear buttons, 3. failure when a scroll bard is embedded in another scrollabel region and it is unclear what scroll to use. failure when scrolls are low contrast.

To define: Easily available mode or setting is one that:

• can be set one time with as a wide a scope as possible (such as using the standards of the OS, ETSI or GPII when available) and
• with the option to save or change the setting, were available interoprabliy but also for a scope of the set of web pages and
• is reachable from each screen where it may be needed, and the path and control conforms to all of this extension.

Instructions, labels, navigation and important information are provided with a clear writing style that includes:

(simple text version: Use a clear writing style)

1. An easy to understand tense and voice. Please refer to the exemptions for changes for a defined scope such as a different location or language.
2. The main task of each page is clarified though the presentation, main heading and page title. Extraneous information is separated or progmatically determinable.
3. Use short clear sentences with a maximum of one conjunction and two commas.
4. Choose words that are in general use for the context. Use word or phrase from the most commonly used 3000 words, unless this will result in a loss of meaning. (Note we may change the number)
5. Avoid hyphenated words and acronyms unless they are the common form to refer to the concept. -http://www.fltr.ucl.ac.be/fltr/germ/etan/bibs/vocab/cup.html
6. Clearly differentiate between facts and less substantiated opinions. (Was rewritten from "Clearly differentiate between opinions and facts " )
7. Reduce ambiguities by:
   1. metaphors and non-literal text are not used or can be automatically replaced via an easy to set user setting and standardized technique. All meaning must be retained when non-literal text are replaced.
   2. identifying each step in instructions,
   3. using specific and concrete wording in instructions,
   4. the meaning of each word should be clear from the word's context, or programmaticly determinable.
8. On controls, links and buttons use words that identify their function. Function can be
   1. the default term used for the function on the user platform or
   2. the function of the button or link (such as "search" in place of "go") or
   3. the destination of a link (such as "home" or "contact us")
9. In menus with sub menus:
   1. the text of each main menu item is easy to understand.
   2. each sub menu item is clearly associated with the main menu item under which it falls (This can be due being an industry or platform default)
10. Double negatives are not used
11. A summary is provided. For pieces of content with less then 200 words the heading may act as a summary.
12. Information that is most likely to be important to the user is easy to find, such that it is:
    1. above the scroll or a clear link to it is above the scroll and
    2. clarified though the presentation such as
       1. they are visually differentiated and accentuated or
       2. they appear before other main content

Techniques include: show words that are common but not the correct context or unclear meaning as a failure
Techniques include: Key points are bold and in a document 
Techniques include: Important information is in a call out box with the right semantics 
Techniques include:  will be a using an active voicing in English and the present tense.
Techniques include: when one sentence comes from a reliable scientific source and the next sentence of "fact" come from a marking department without reliable scientific study, it should be signposted that latter is an opinion. A second technique sponsored content is clearly marked as coming from other sources.

To define: concrete wording, non-literal, non-trivial information - as information that a user might need or have searched to find out

To define: Important information as:

1. information the user may need to complete any action or task including an offline task.
2. information the user may need to know related to safety, risks, privacy, health or opportunities.

(COGA Techniques 2.5)

To define: most commonly use 3000 words - any credible word list may be used and audience may be taken into account in conducting the word list. So , for example, if the audience is young, blog will be in the 3000 words. You may however have a site for retirees the word list may be different. If it is not included in the techniques the author should publish what word list was used.

Exemptions: 1. There are times when passive voicing or other tense can be clearer. Other voicing may be used when it has been shown via user test to be easier to understand, more friendly or appropriate.

2. The present tense is not required when describing or discussing past or future events.

3. If the writing style is an essential part of the main function of the site, such as a literary work.

4. Where less common words are found in user testing to be easier to understand for the audience (user testing should included people with cognitive disabilities that could e in the target audience - need further definition )

5. The writing style items may be replaced for a location or type of content were user testing has shown a more effective writing style to aid comprehension for people with cognitive disabilities. Such as for content written in a specific language.

6. The content will be penalized for not conforming to a given writing style (such as a dissertation or PHD proposal)

To define: non-trivial information: Information the user may find important or need to know , such as infromation that the user may have searched to find. - coment - may be to vage. information can be non trivial but noone NEEDS to know it

When there is a barrier between the content and the user that requires additional abilities an alternative is provided that does not require additional abilities.

Additional abilities include cognitive functions that are required, but are not necessary to achieve the main task for which the content was designed. Such as:

• Capture or security mechanisms that require copying, spelling or memory skills,
• Interactive communication systems, voice menu systems such as Voice XML automated customer service portals, which require the user to have a good working (transitory) memory. The user needs hold pieces of transitory information in the mind such as the number that is being presented as an option, whilst processing the terms that follow.
• Hiding of critical features under categories that are hard to understand. Such as a Web Of Things interfaces, that requires the user to understand the word "mode" to get to easy to understand options.

Exception: There is an exception when there is a not a known alternative that provides the same main function and does not rely on additional abilities. A known alternative can be a WCAG technique, W3C note, or in the documentation of the platform.

Technique examples 

Examples in security: 
Web security and privacy technologies, for example, intentionally require users to perceive more and to do more to complete tasks. Three examples of these technologies are passwords, CAPTCHA, and 2-Factor Authentication. Such techniques require that the user has a good working memory or short term memory required to copy a code or remember complex passwords.	

Alternatives exists that can allow more people to use content securely. These alternatives include using Web tokens, signing in via email account or other account, or biometrics are all alternatives to the above. For more details on this issue and on alternatives are available https://rawgit.com/w3c/coga/master/issue-papers/privacy-security.html

 In voice systems this may include,
* Requiring the user to understand categories,
* Requiring the user to remember numbers

Can all be used as a barrier to getting human help. It is avoidable by having 0 as a reserved digit to access a human operator and by using best practices.  For more details on this issue and on alternatives are available https://rawgit.com/w3c/coga/master/issue-papers/voice-menus.html

 In the Web of things this may include: 
* remembering what symbols mean
* remembering sequences to run certain tasks

This is avoidable by having simple text with symbols and clear discoverability of how o complete each task and recoverability from errors. Most user interfaces are designed to help users complete tasks. However, sometimes they can introduce barriers that are not necessary for using the content.  When an author makes design choices that mean people who could have used their content now can not, that content is not accessible. 

Note: we need to define "cognitive function"

Under WCAG 3.2 Make Web pages appear and operate in predictable ways.

We suggest adding the following success criteria:

A predictable design is used within a set of pages that includes:

(see COGA Techniques 2.4)

• A consistent layout of common elements
• Consistent use of icons and controls such that the same icons and buttons serve the same function
• The standard layout design and common icons are easily available.

Technique: Making common components and icons programmatic determinable enables their positions to be standardized via personalization.

Define: enabling easy to use personalization -which is discussed above

Define: standard layout design as:

1. recommended in a wcag technique (techniques can be submitted by any other standard and just approved by wcag) or
2. by the user platform
3. or in a W3C note

Technique: Example of coga-wcag technique In 2015 in English sites standard layout for web sites includes: 
#the search box is in the right hand corner
#a link to home page in the left hand corner
#site map  in the footer, etc.
#main menus are at the top of the page under the log and search or on the left hand side.

Technique: Common icons include:
# icons used in a standard or common operating system.
# a question mark for help
# an exclamation mark for warnings

Under WCAG 3.3 Help users avoid and correct mistakes.

We suggest adding the following success criteria:

The success or failure of every action should be clearly indicated to the user and visual rapid feedback should be available. Spoken feedback should be a user selectable option.

(COGA Techniques 2.6 )

To define: easily-recognizable such as 99% of the intended audience will recognize this as feedback for the action of the action, such as a tick or a green traffic lite to green with a word such as "correct"

To define: clearly indicated success or failure: Confirm that after a user action the user known that the action was successful or not. Applications should also let the user know what just happened and where they are in a process.

To define: an option for spoken feedback: Spoken feedback is often more effective then written feedback. However having both spoken feedback and longer lasting written and visual feedback helps the user know where they are and restores the context if attention is lost. Spoken feedback can annoy and distract some people so spoken feedback should be available as an option and in response to a user preference setting when available.

To define: rapid: less then 200 ms (from etsi)

Technique an email is sent, It does not just disappear but the  user can be told "your email was sent".

Support is provided that help users understand the content, that includes:

(See COGA Techniques 2.7 )

• Known standardized API's for tools that help the user understand and use the content are supported. (Such as synchronized speech, password management tools, simplification and others) To define known standardized API's as identified in the platforms documentation or in a WCAG technique or W3C publication
• Short tooltips on all icons and jargon that clarify the meaning are provided (COGA Techniques 2.7. ) To define jargon as a type of language that is used in a particular context and may not be well understood outside of it.
• Charts or graphics are provided where they aid the comprehension of complex information (COGA Techniques 2.7.3 )
• Tables are provided where they aid the comprehension of information
• Symbols are provided to help the user identify key content including: types of contact information, main functions, warnings, key points,
• The content owner identifies keywords that aid comprehension for the user and any keywords are programmatic determinable or visually emphasized.
• Standardized techniques to support interoperable symbol sets are used when available. (To define Standardized techniques as above)
• Techniques are used to help the user find information that incudes:
  • A clear navigational path is provided to all content that:
    • Use clear headings, menu names and categories to signpost information. It should be clear how content correlates to each signpost in its navigation path.
    • Each page can be reached though any high level page that it logically could belong.
    • Were there are more then five links directly under any one navigation heading or subheading it is examined to see if adding additional category would be helpful. (AAA)
    • There are no more then no more than three clicks to get to information from a landing page or portal. (AAA)
  • Help and support page or function should be reachable with one click. When human help is available the correct contact information or mechanism should be reachable within two clicks.
• Provide a search box. Exception is provided were adding a search box is a significant expense for the site
• For multi media it should be easy to jump to each section of the content
• Allow reading of long form of acronyms
• Where an understanding of math is not a primary requirement for using this content. Reinforce numbers with non-numerical values, e.g., Very Cold, Cold, Cool, Mild, Warm, Hot, Very Hot.
• Enable the default format and standards of locale and allow for change of format

Note we will need to define a process for what techniques get added, that includes independent research that show the benefit. If the benefit is contested the WG decides.

Techniques include: a small site without access to their servers and can n install a free site search
Techniques include: indexing and bookmarks in a video. 
Techniques include: 
*Temperature
**Use the default temperature format of locale and allow for change of format
**Allow reading of long form temperature.
 techniques include using a acronym attribute on a C that reads "centergrade"
**Reinforce with non-numerical values, e.g., Very Cold, Cold, Cool, Mild, Warm, Hot, Very Hot.
*Calculations - Ability to have mathematical notation read out with text to speech to aid understanding.
* Currency - Consider placement of currency symbols related to locale and offer acronym with explanation or full text
* Buying & Selling Online (Quantities & Size) -Do not rely on numbers alone when describing goods. Provide a hint or additional information to aid users
* Do not rely on numbers alone when describing goods. Provide a hint or additional information to aid users.
Technique to include: personalization  used to remove extraneous information and reduce the clicks.
Technique to include: 1,use testing to find what helps, 2, identifying any words that may make the user realize this is relevant content, 3, identifying that there are no keywords that aid comprehension for example, when all keywords short sections are used under clear headings.
 Techniques include:  using see also to alow a user to reach related content that is not in this path. A link to a site map which has all the content in it can also be sufficient

To define:

• jargon - words or expressions used by a group that is typically difficult for others to understand.
• api's that help the user: api's ,must be included as a technique and include E-Wallets & password management, text to speak with synchronized highlighting - Use of synchronized highlighting, of complex graphics and formula with speech (COGA Techniques 2.7.3 )
• complex information
• Keywords that aid comprehension

Note WCAG/COGA will develop clear guidelines for acceptance criteria, such as backed up by research - similar to the COGA criteria for research.

Support is provided that help users complete and check their task, that includes

(may be provided via a standard personalization mechanism) (COGA Techniques 2.9 )

1. Use known techniques to minimize errors that are relevant to the content
2. Clear visual indicator are provided that identify what information is essential, and non essential information is clearly differentiated from essential information.
3. Instructions are provided in the following cases:
   1. If there is not a label does that fully describe the control, provide instructions that explains purpose and usage of the control
   2. If it is not clear were to get the required information, instructions are provide. (Graphics with a text alternative may be sufficient) ( A clear instruction or information is on where 99% of your target audience understand immediately what to do)
4. All standard ways of representing information are accepted as input formats, such as different ways of writing a phone number and date formats.
5. Documented common input errors are corrected automatically (define Documented common input errors as identified in a techniques)
6. A summary is provided before submitting important information. (already in wcag as an option, ut this is the best option for coga)
7. Non native content and sponsored content are clearly marked and visually differentiated by standardized techniques
8. Critical features can be without use of a scroll bar
9. Options that may disadvantage the user are only selected at the users specific request. All types of charges must be clear at the start of a transaction task. When a minimum is known for a type of charge it must be be made clear at the start of the transaction task.
   1. A simple mechanism is provided to allow the user to undo mistakes. The user can repair information via clearly labeled action and get back to the place they were at, in one clearly labeled action with unwanted loss of data.
   2. A user can go a step back in a process via one clearly labeled action (exceptions may be required)
   3. Where a standard mechanism exists for the platform or technologies exist for context sensitive help it should be used.
   4. All icons and jargon have a short explanation available. Where a standard mechanism exists for the platform or technologies it should be used.
   5. Where human help is provided, it is available via one clearly labeled action for each web related modality for which the help is available.
   6. Enable the user to set a reminder for date and time sensitive events. Reminders should be set only at the users request. Where a standard mechanism exists for the platform or technologies it should be used.

To define: "known techniques " as any wcag techniques or platform official documentation for any technologies used

To define: essential information as information that is required by the application to complete the task requested by the used. Clear visual indicator is one that 99% of your target audience understand)

To define: web related modality - such as email, VOIP phone, chat - but excluding snail mail and not if support is not provided to the public. (COGA Techniques 2.10.2 )

To define minimum known for a type of charge - is when this is a charge that is incurred 90% or more of the time with this traction. Charges that you almost always you have to pay such as airport tax. or any seat on an airplane not just a preferred seat). User request is a selection by the user that 99% of the target audience understand the implication.

To define the target audience as people use this content.

Techniques to include:  common controls includes just adding a attribute such as coga-action="undo" to enable extra support automatically

Techniques to include:   javascript that enables common forms of phone numbers to morph a single notation

Techniques to include:  the post code being written in the text field with the city or state information

Techniques to include:  advertisements in a box clearly marked as "advertisement"

Techniques to include:  increasing the number of items (such as having a default of two) if the user may not notice.  Increasing have hidden charges that are only brought to the users attention after they have given their credit card information.  Failure is any  attempt to r trick the user into buying or agreeing to something that they did not understand, or create a price structure that is unclear. note our users deferentially worse effected by these things.

Techniques to include: use coga/aria extension for standard elements Note that using this sematics all content can easily conform 

Techniques to include: tooltips and coga extention) (COGA Techniques 2.10.2 )

Techniques to include:
* Buying & Selling Online (Payments)
**Do not ask users to enter credit card details unless needed for a specific purchase.
**Allow pasting of password and payment details into form fields. (Editors note- an exception may be required) See also avoiding additional layers of password authentication (e.g., verified by Visa or time sensitive random security numbers).See also: Web Security and Privacy Technologies
*Format
**Break up card input forms to match credit cards, e.g., 4x4 numbers.
**Different cards have different patterns of numbers eg Amex may have more numbers than Standard Cards. Payment forms usually ask the user for the type of card. The card input form should reflect the payment card type.
includes: (COGA Techniques 2.9.3 )

Techniques to include:
##Calendars and dates
###Calendars should default to the first relevant day. Work calendars should default to first working day of a user's locale. 
###The user can not enter invalid dates. If the user tries to select an invalid date it must be clear why a date can not be selected such as with a short clear and friendly error message (for example "sorry that date has passed). This avoids abandonment of the process.
###Calendar based booking systems must avoid ability to book return date before departure date.
###Terms are used  that describe the present past and future days rather than just using numbers or dates. By using terminology such as today, tomorrow or travel now in the appropriate language for the locale, the user has a clear understanding of the timeliness of the event, booking or occasion.
###Display long form of dates with punctuation, e.g., June 1st, 2015 or 1st June, 2015. This offers a clear understanding of the date. Punctuation helps the text to speech API read the date in a way that is easier to follow.
###When using numbers for time - check use of appropriate punctuation between numbers when providing times as these may be read inappropriately by text to speech engines.
##Temperature
###Use the default temperature format of the locale. The requirement to convert between Centigrade and Fahrenheit and vice versa is burdensome so defaulting to the format of the locale removes one layer of complexity.
###Allow reading of long form temperature. Reading the values long form rather than using figures is helpful in for the same reasons outlined in the dates and calendar section.
###Reinforce with non-numerical values, e.g., Very Cold, Cold, Cool, Mild, Warm, Hot, Very Hot. These are subjective values and may not always be helpful especially when dealing with weather and ambient temperature (due to reasons such as variances in regional average temperature - what is considered hot in UK is considered cool in India or Thailand). It may be possible to use look up tables and JSON to query relative average temperature based upon locale and adjust temperature ranges accordingly.

Provide mechanisms that help the user focus and restore context if attention is lost.

(Remove uncertainty and help the user maintain context)

This includes:

1. Use known techniques that remind the user of the context, including:
   1. Pointers to remind the user of the current task. Pointers should not distract the user when they choice to change tasks without the users concent.
   2. In the scope of a task, reminders of broader context. For a non-complicated task, such as reading a home page, clearly identifying the site and it's aim is sufficient.
2. Where a site may generate interruptions, a clearly labeled mechanism is provide to enable the user to control them,(COGA Techniques 2.11.1) such that:
   1. Interruptions can be easily controlled and turned off
   2. Secondary content (such as special offers or complementary material) can be easily controlled and turned off.
   3. No sudden changes occur on the site.
   4. Media events can be easily controlled and turned off.
   5. Chat can be easily turned off and on again.
   6. Non-critical messages can easily be turned off and on again
   7. Where a standard mechanism exists for the above it should be used.

See (No Interruptions COGA Techniques 2.11.2, - Help The User Focus COGA Techniques 2.11.3, and Help the user find information COGA Techniques 2.11.4)

Techniques to  include
*Headings and titles are provided that provide context 
*In multi step process both the process and the  step are identified  (technique = For Items like breadcrumbs can help orientate the user and help the user restore the context when it is lost. (Making breadcrumbs clickable can also help the user undo mistakes.)  
*Any choices made by the user in a process are easy to review in one clearly labeled action and the user can get back to the place they were at, in one clearly labeled action.
*if you have a calendar/mail program you should provide a feature that could notify the user of an impending meeting or to dos (broader scope)
*for a non complicated task the site is identified (broader scope)

Items where new techniques are WCAG 2.0 required

1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

The following are techniques under development. We can not recommend their use until they have been proven to work reliably.

• 1 Add technique to enable interoperable symbol mapping for products for Non verbal people.

In the Web Content: Syntax: aria-concept = "uri". Example (Pseudocode): <img aria-concept="http://wordnet.org/somepage#girlnode" scr="girlwithbow.gif" />

• 2 Add technique at a useragent symbol file end:

<mysymbol scr="girlwithskirt.gif" aria-concept="http://wordnet.or g/somepage#girlnode" lang="en" /> Note this is not about standardizing the symbols but a way of mapping them

Items where WCAG 2.0 SC levels should be changed

We recommend the following level AAA are considered more important for COGA

1.4.7 Low or No Background Audio No Background: The audio does not contain background sounds or Turn Off: The background sounds can be turned off.

We would need to change it as well to - Turn Off: The background sounds can EASILY be turned off.

1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA)

1. Foreground and background colors can be selected by the user.
2. Width is no more than 80 characters or glyphs (40 if CJK).
3. Text is not justified (aligned to both the left and the right margins).
4. Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
5. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.

Note 2.4.8, 3.3.5, 2.2.3 No Timing and 2.2.5 Re-authenticating has been addressed above

2.4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)

We would want to lose the text "except where the purpose of the link would be ambiguous to users in general"

2.4.10 Section Headings: Section headings are used to organize the content. (Level AAA) Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.

3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA)

3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA)

3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA)

Note that this may need exceptions but most exceptions would still require a summary at an easier reading level.

3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

3.3.6 Error Prevention (All): For Web pages that require the user to submit information, at least one of the following is true: (Level AAA) Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

We would want a change that ALL are required.

Edits to WCAG

Contrast The visual presentation of text and images of text AND ICONS have a contrast ratio of at least

 Add dyscalculia examples!!!